Implement store specification #12
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit introduces the Store API, enabling persistent and reactive data storage within the Render SDK. It includes support for various storage backends, validation, transactions, and reactive publishers. Co-authored-by: max.mrtnv <max.mrtnv@gmail.com>
|
Cursor Agent can help with this pull request. Just |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement the Store API specification to provide a flexible and reactive key-value store for the Render SDK.
This PR delivers the complete Store API, including core data models, scope and storage enums, a validation system, reactive Combine publishers, five storage backends (Memory, UserDefaults, File, ScenarioSession, Backend), a store factory with version management, and integration with
RenderSDKfor component binding and debugging.